Workstation Deployment

ABSTRACT

Deployment of a workstation includes receiving data related to the computing environment of workstations, organizing the workstations into groups based on at least one selectable common attribute among the data, and producing a deployment schedule based on the groups.

This Application is a continuation of application Ser. No. 10/139,759,entitled “Workstation Deployment,” filed on May 6, 2002, the entiredisclosure of which is incorporated herein by reference.

TECHNICAL FIELD

This disclosure relates to workstation deployment, such as, for example,a deployment of software onto one or more workstations distributedacross an enterprise.

BACKGROUND

A typical enterprise may have a large number of computer workstationsdistributed over wide geographic areas spanning across different citiesor countries. Each of the workstations can be configured with acomputing environment that may include different and often incompatiblehardware components and software components such as different operatingsystems or application programs. The computing environment may have tobe upgraded or replaced with a new computing environment because thecurrent computing environment may have become obsolete.

To deploy a new computing environment onto one or more workstationsdistributed across an enterprise often requires overcoming a largenumber of logistical problems. Factors such as the number and type ofworkstations in the enterprise must be considered. Moreover, it may bedifficult to gather and analyze information related to the computingenvironment of all the workstations in an enterprise.

SUMMARY

In an implementation, a method includes receiving data related tocomputing environments of a plurality of workstations and organizing theworkstations into groups based on at least one selectable commonattribute among the received data. A deployment schedule is produced,the deployment schedule comprising at least one of the groups anddefining a time frame during which the workstations organized into theat least one of the groups are to receive a deployment.

In another implementation, an apparatus includes a processor coupled toa memory. The processor is configured to receive data related to acomputing environment comprising a plurality of workstations andorganize the workstations into groups based on at least one selectablecommon attribute among the received data. The processor is alsoconfigured to produce a deployment schedule comprising at least one ofthe groups, the deployment schedule defining a time frame during whichthe workstations organized into the at least one of the groups are toreceive a deployment.

In various implementations, one or more of the following advantages maybe provided. The deployment process can produce a deployment schedulefor a large number of workstations distributed over wide geographicareas that may span across different cities or countries. The deploymentprocess can gather and analyze information related to the computingenvironment of these disparate workstations. The deployment process cantest and monitor the process of verifying whether the new operatingsystem that is to be deployed on the workstation functions properly withthe application programs on the workstations. As a result, an enterprisewith a large number of workstations can receive a new computingenvironment that can include a new operating system and applicationprograms that properly operate with the new operating system.

The deployment process may help improve the workflow associated with theprocess of deploying workstations. The process centralizes thedeployment activities by having business departments identify the timeframe in which the deployment schedule is to be executed. The progressof the deployment activities can be monitored automatically by a singlecentralized database. The deployment schedule can provide the members ofa deployment team a list of the users, type of hardware, software, orspecific configuration each workstation is to receive. As a result, theprocess can be performed in a timely manner by improving thecoordination of the efforts of administrative personnel responsible fordeploying the new computing environments.

DESCRIPTION OF DRAWINGS

FIG. 1 is a simplified block diagram of a workstation deployment system.

FIG. 2 is a detailed block diagram of a server computer according to anexample implementation.

FIG. 3A is a diagram of data related to the deployment scheduleaccording to an example implementation.

FIG. 3B is a diagram of data related to the new computing environmentaccording to an example implementation.

FIG. 4 is a flow chart according to an example implementation.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a simplified block diagram of a workstation deployment system10 according to an example implementation. The deployment system 10includes one or more workstation computers 12 wherein each workstationis configured to operate according to a computing environment 14. Thecomputing environment 14 can include information such as theorganizational entity associated with the user of the workstation, thegeographic location of the workstation, the hardware or softwarecomponents residing or executing on the workstation, or otherinformation. The software components can include an operating system,device drivers, application programs, or other software components. Theworkstation computers 12 communicate with a server computer 22 over anetwork 16 such as a wired or wireless network.

The server computer 22 includes a deployment process 24 that gathers andanalyzes information related to the computing environment 14 of each ofthe workstations 12. The deployment process 24 produces a deploymentschedule 20 that is based on the computing environment 14 of each of theworkstations. The deployment schedule is maintained in a database 18.The deployment process 24 creates a new computing environment 26 for theworkstations 12. The new computing environment 26 can include softwarecomponents such as a new operating system, application programs, devicedrivers, or other software components. The deployment process 24 anddeployment environment 20 facilitates the deployment of the newcomputing environment 26 onto the workstations 12.

FIG. 2 is a detailed block diagram of a server computer 22 according toan example implementation. The server computer 22 can be implemented asa single server computer that includes a computer bus 30 connecting acentral processing unit (CPU) 32 to memory 36. The CPU 32 is capable ofexecuting programs 38 residing in memory 36 and processing data storedin memory. The programs 38 can include an operating system such asMicrosoft Windows 2000 server, device drivers for handling low-levelaspects of hardware components, application programs such as MicrosoftOffice, or other programs. The CPU 32 can include and Intel Pentiumprocessor or other processor. The memory 36 can be a combination of readonly memory (ROM), random access memory (RAM), static RAM (SRAM),dynamic RAM (DRAM), or other memory.

The memory 36 also includes the deployment process 24 which can beimplemented as a set of software instructions adapted to gather andanalyze data such as the computing environment 14 from the workstations12 and produce the deployment schedule 20. The deployment process 24uses a graphical user interface (GUI) to allow the display or update ofthe deployment schedule 20. The deployment process 24 is alsoresponsible for providing the new computing environment 26 that theworkstations are to receive according to the deployment schedule 20. Thenew computing environment 26 is stored in memory 36 but can be stored inthe database 18 or some other storage resource on another computer. Thedeployment process 24, the deployment schedule 20, and the new computingenvironment 26 is described in further detail below.

An input/output (I/O) controller 34 is used to couple the servercomputer 22 to hardware and software components such as the database 18,the network 16, a display device 28, an input device 29, or othercomponents. The database 18 can be used to store data related to theexecution of the programs 38 including data related to execution of thedeployment process 24 such as the deployment schedule 20. The database18 can be implemented using a database management program such asMicrosoft SQL 2000, Oracle, Sybase, or other database managementprogram.

The display device 28 can include a computer display capable ofdisplaying data related to the execution of programs on the servercomputer 22. For example, the display device can display data associatedwith the deployment schedule 20 during the execution of the deploymentprocess 24. The input device 28 can include a pointing device such as amouse, track ball, light pen, touch sensitive display, or other type ofperipheral device and may be used in combination with a keyboard toinput data into the programs 38 executing on the server computer 22.

The I/O controller 34 can include hardware and software components forconnecting the server computer 22 to the network 16. The server computer24 is capable of communicating over a wired or wireless network such as,for example, a local area network (LAN), wide area network (WAN),Ethernet, the Internet, or other network. In the above discussion, theworkstations 12 have been described as computers having computingenvironments 14 that are typically operated by users in an enterprise.However, any computer, such as one of the workstations 14, can beconfigured as an administrative computer to access the server computer22 for the purpose of executing the deployment process 24, producing thedeployment schedule 20, and providing the workstations 12 with a newcomputing environment 26.

FIG. 3A is a diagram of data related to a deployment schedule 20according to an example implementation. The deployment process 24produces the deployment schedule 20 based on data related to thecomputing environment 14 of the workstations 12. The deployment schedule20 includes an entry 62 for each user or workstation 12. Eachworkstation entry 62 includes a user field 50 identifying theworkstation with attributes such as the name of the user of theworkstation 14, a computer identification number of the workstation,and/or some other unique identifier.

The workstation entry 62 also includes a computing environment section52 that has a hardware (H/W) field 52 a, a software (S/W) field 52 b, adepartment field 52 c, and a region field 52 d. The data in thecomputing environment section 52 is based on the computing environment14 gathered from the computer workstations 12. The H/W field 52 a cancontain data related to the type of hardware the workstation containssuch as the type and amount of storage, the type and amount of memory,the type of graphical display, the type of network card, or other typeof hardware related data.

The S/W field 52 b contains data related to software executing orresiding on the computer workstation 12. Such data can include the typeof operating system, device drivers, application programs, or otherdata. The department field 52 c contains data identifying anorganizational entity associated with the workstation. An example ofsuch data includes a department within an enterprise such as anaccounting department, a legal department, marketing department, orother data. The geographical location, such as a city or country, of thelocation of the workstation 12 is represented by data in the regionfield 52 d.

The time to deploy field 54 indicates date and time information relatedto when the workstation 12 is to receive the new computing environment26. The time to deploy field 54 can be used by the deployment process todetermine when an alert should be sent to the user of the workstation 12indicating the time frame when the workstation is to receive the newcomputing environment 26. The status field 56 represents the status ofthe deployment process such as data indicating whether the workstation14 has received the new computing environment 26. The application todeploy field 58 includes data indicating the name and status of theapplication programs that each of workstations 12 is to receive.

The deployment process 24 can produce the deployment schedule 20 byorganizing each entry 62 into groups of workstations 60 based on aselectable common attribute among the data in each entry 62. Forexample, the workstations can be organized according to the type ofhardware residing on the workstation represented by the H/W field 52 a.Likewise, the software residing on the workstation represented by theS/W field 52 b can be used to organize the workstations. Moreover, otherfields can be used to organize the groups of workstations 60.

FIG. 3B is a diagram of data related to the new computing environment 26according to an example implementation. The new computing environment 26that the workstations 12 are to receive is represented by a datastructure having a new operating system field 26 a, application programsfield 26 b, and a device drivers 26 c field. In one embodiment, the newoperating system 26 a field can refer to an operating system such asMicrosoft Windows XP, the application program field 26 b can refer to anapplication program such as Adobe Acrobat, and the device driver 26 cfield can refer to a device driver such as a network card driver. Thedeployment schedule 20 keeps track of these software componentsindicated in the new computing environment 26, but the actual softwarecomponents may be stored in the memory 36 of the server computer 22, ina separate portion of the server computer 22, or on a separate computer.

FIG. 4 is a flow chart of the deployment process according to an exampleimplementation. The server computer 22 receives 70 data related to thecomputing environment 14 of the workstations 12. As described above,each user or workstation 12 is assigned an entry 62 in the deploymentschedule 20 and each entry is stored in the database 18. The data foreach entry 62 in the computing environment section 52 can be obtained bya combination of inventory tools such as SMS provided by Microsoft. Thedata also can be imported from other source of data such as contactmanagement programs, electronic mail (E-mail) programs, or other sourcesof user data.

By gathering this information in a single location such as the database18, problems can be identified before the workstations receive the newcomputing environment 26. For example, the information can revealwhether a particular application program residing on the workstation 12is compatible with the new operating system that is part of the newcomputing environment 26. In addition, the information can revealwhether the current hardware on the workstation 12 is adequate for thenew operating system that the workstation is to receive.

As mentioned above, the S/W field 52 b can contain the names ofapplication programs residing on the workstation 12. The deploymentprocess 24 is able to map the names of the application programscontaining “exe” extensions into a generic program name for ease ofprocessing. This mapping process allows software administrationpersonnel to quickly verify the names of the application programs usinga single name rather then to have to search through a list ofapplication programs containing numerous “exe” extensions.

The time to deploy field 54 can be set to a time frame indicating a timeand date when each of the workstations 12 is to receive the newcomputing environment 26. The time frame can be based on factors such asthe availability of the workstation 12, the amount of data trafficexperienced by the network 16 during a particular time frame, theavailability of the application programs that comprise the new computingenvironment 26, or other factors. The status field 56 can be set to avalue indicating whether the workstation 12 has received the newcomputing environment 26.

The application to deploy field 58 can be set to a value to indicate thename and status of each if the application programs that comprise thenew computing environment 26. Executing the deployment schedule 20involves deploying a new computing environment 26 that can include a newoperating system and one or more application programs. Before thedeployment schedule 20 can be executed, the deployment process 24verifies whether the application programs can properly operate with thenew operating system. Such a verification process includes installingthe new operating system and one or more application programs on a testworkstation and testing whether the application program properlyoperates under the new operating system. Once the operation of theapplication program has been verified, the value of the application todeploy field 58 can be updated to indicate the application program isready for deployment.

Once the data related to the computing environment 14 has been receivedfrom the workstations 12, the server computer 22 organizes 72 theworkstations into groups 60 based on at least one selectable commonattribute among the data. The common attribute can be selected based onfactors such as the number of geographic locations and number ofworkstations at each location, the number of departments and the numberof workstations assigned to each department, the type of hardware andsoftware installed on the workstations, or other factors. Moreover, eachgroup 60 can be further subdivided into one or more sub-groups. Forexample, the workstations 12 can be grouped into regions based on theregion field 52 d and that group can be further subdivided into asub-group that includes the type of hardware components installed oneach the workstations based on the data in the H/W field 52 a.

Once the workstations 12 have been organized, the server computer 22produces 74 a deployment schedule 20 based on the results of organizingthe workstations. The deployment process 24 analyses the deploymentschedule 20 and determines whether the workstations 12 indicated in thedeployment schedule are prepared to receive the new computingenvironment 26. For example, the application to deploy field 58 isexamined to determine whether the application program listed in thefield has been verified and is ready to be deployed to the workstation12. If the deployment schedule 12 indicates that the application programhas been verified, then a message, such as an E-mail, can be sentnotifying the user of the workstation of the time frame in which theworkstation is to receive a new computing environment 26.

The deployment process 24 provides 76 a new computing environment 26 tothe workstations 12 according to the deployment schedule 20. Thedeployment schedule 20 can be viewed and updated by systemadministrative personnel using the GUI 42 portion of the deploymentprocess 24. The deployment schedule 20 is updated during the process ofdeploying the computing environment 26 to the workstation 14. Forexample, the status field 56 associated with a workstation can beupdated to indicate whether the workstation has received a new computingenvironment 26.

As mentioned above, the new computing environment 26 can include a newoperating system and application programs that have been verified tofunction properly with the new operating system. The actual operatingsystem and application program that comprises the new computingenvironment 26 can be maintained by a separate program on the servercomputer 22, on a separate computer, or a distributed among acombination of computers. In one embodiment, when it is time for theworkstation 12 to receive the new computing environment 26, thedeployment process 24 can send a signal to a separate process that isresponsible for sending the software components that comprised the newcomputing environment 26 to the workstation 12. The separate process canrespond by sending the software components comprising the new computingenvironment 26 to the workstation 12 indicated in the signal.

The deployment process 22 also can handle post deployment functions oncethe workstations 12 have received the new computing environment 12. Forexample, workstations 12 may be geographically located close to eachother and may include configuration information that enables them toshare a common resource such as a printer. The deployment process 24 canrestore the configuration information after the workstation has receivedthe new computing environment 26 so that the workstation can continueusing the shared resource as it had done before the new computingenvironment. Likewise, other configuration information such as accountnumbers, password access, shared storage resources such as a hardrive,or other configuration information can be restored so that thedeployment and operation of a new computing environment 26 on theworkstation appears seamless to the user of the workstation.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention. Forexample, the deployment process 20 can produce a deployment schedulethat is distributed among one or more databases. Accordingly, otherembodiments are within the scope of the following claims.

1. A computer-implemented method comprising: receiving data related tocomputing environments of a plurality of workstations; organizing theworkstations into groups based on at least one selectable commonattribute among the received data; and producing a deployment schedulecomprising at least one of the groups, the deployment schedule defininga time frame during which the workstations organized into the at leastone of the groups are to receive a deployment.
 2. The method of claim 1,wherein the data includes at least one of an organizational entityassociated with the workstations, a geographic location of theworkstations, or the hardware or software residing on the workstations.3. The method of claim 1, wherein the common attribute among thereceived data includes at least one of an organizational entityassociated with the workstations, a geographic location of theworkstations, or the hardware or software residing on the workstations.4. The method of claim 1, further comprising maintaining the deploymentschedule on a database.
 5. The method of claim 1, wherein the deploymentschedule includes an entry indicating availability of a program to beused in producing the deployment schedule.
 6. The method of claim 1,wherein the deployment schedule includes an entry indicating a timeperiod during the time frame in which each of the workstations is toreceive a program.
 7. The method of claim 1, further comprisingproviding a new computing environment to the workstations.
 8. The methodof claim 7, wherein the new computing environment includes at least oneof an operating system, application program, or device drivers.
 9. Anapparatus comprising: a memory; and a processor coupled to the memory,wherein the processor is configured to perform operations comprising:receive data related to a computing environment comprising a pluralityof workstations; organize the workstations into groups based on at leastone selectable common attribute among the received data; and produce adeployment schedule comprising at least one of the groups, thedeployment schedule defining a time frame during which the workstationsorganized into the at least one of the groups are to receive adeployment.
 10. The apparatus of claim 9, wherein the data includes atleast one of an organizational entity associated with the workstations,a geographic location of the workstations, or the hardware or softwareresiding on the workstations.
 11. The apparatus of claim 9, wherein thecommon attribute among the received data includes at least one of anorganizational entity associated with the workstations, a geographiclocation of the workstations, or the hardware or software residing onthe workstations.
 12. The apparatus of claim 9, further comprising adatabase to maintain the deployment schedule.
 13. The apparatus of claim9, wherein the deployment schedule includes an entry indicatingavailability of a program to be used in producing the deploymentschedule.
 14. The apparatus of claim 9, wherein the deployment scheduleincludes an entry indicating a time period during the time frame inwhich each of the workstations is to receive a program.
 15. Theapparatus of claim 9, wherein the deployment comprises a new computingenvironment to the workstations.
 16. The apparatus of claim 15, whereinthe new computing environment includes at least one of an operatingsystem, application program, or device drivers.
 17. Acomputer-implemented method comprising: receiving data related to thecomputing environment of workstations at a server; organizing theworkstations into groups associated with the workstations based on atleast one selectable common attribute among the data; and automaticallyproducing a deployment schedule comprising at least one of the groupsand based on the computer environments of the workstations of at leastone of the groups.
 18. The method of claim 17, wherein the data includesat least one of an organizational entity associated with theworkstations, a geographic location of the workstations, or the hardwareof software residing on the workstations.
 19. The method of claim 17,wherein the common attribute among the data includes at least one of anorganizational entity associated with the workstations, a geographiclocation of the workstations, or the hardware or software residing onthe workstations.
 20. The method of claim 17, further comprisingmaintaining the deployment schedule on a database.
 21. The method ofclaim 17, wherein the deployment schedule includes an entry indicatingavailability of a program that is included in a new computingenvironment.
 22. The method of claim 17, wherein the deployment scheduleincludes an entry indicating a time period in which each of theworkstations is to receive a program.
 23. The method of claim 17,further comprising a deployment of a new computing environment to theworkstations.
 24. An apparatus comprising: a memory; and a processorcoupled to the memory, wherein the processor is configured to: receivedata related to the computing environment of workstations; organizeworkstations into groups associated with the workstations based on atleast one selectable common attribute among the data; and automaticallyproduce a deployment schedule comprising at least one of the groups andbased on the computer environments of the workstations of at least oneof the groups.
 25. The apparatus of claim 24, wherein the data includesat least one of an organizational entity associated with theworkstations, a geographic location on the workstations, or the hardwareor software residing on the workstations.
 26. The apparatus of claim 24,wherein the common attribute among the data includes at least one of anorganizational entity associated with the workstations, a geographiclocation of the workstations, or the hardware or software residing onthe workstations.
 27. The apparatus of claim 24, further comprising adatabase to maintain the deployment schedule.
 28. The apparatus of claim24, wherein the deployment schedule includes an entry indicatingavailability of a program that is included in a computing environment.29. The apparatus of claim 24, wherein the deployment schedule includesan entry indicating a time period in which each of the workstations isto receive a program.
 30. The apparatus of claim 24, the processorfurthered configured to provide a new computing environment to theworkstations.
 31. The apparatus of claim 24, wherein the new computingenvironment includes at least one of a operating system, applicationprogram, or device drivers.
 32. An apparatus comprising: a memory; and aprocessor coupled to the memory, wherein the processor is configured toaccess a system that is adapted to perform operations comprising:receive data related to a computing environment comprising a pluralityof workstations; organize the workstations into groups based on at leastone selectable common attribute among the received data; and produce adeployment schedule comprising at least one of the groups, thedeployment schedule defining a time frame during which the workstationsorganized into the at least one of the groups are to receive adeployment.
 33. The apparatus of claim 32, wherein the common attributeamong the data includes at least one of an organizational entityassociated with the workstations, a geographic location of theworkstations, or the hardware or software residing on the workstations.34. The apparatus of claim 32, wherein the deployment schedule ismaintained on a database.
 35. The apparatus of claim 32, wherein thedeployment schedule includes an entry indicating availability of aprogram to be used in producing the deployment schedule.
 36. Theapparatus of claim 32, wherein the deployment schedule includes an entryindicating a time period during the time frame in which each of theworkstations is to receive a program.
 37. The apparatus of claim 32,wherein a graphical user interface is used for displaying or updatingthe deployment schedule.
 38. The apparatus of claim 32, wherein thedeployment comprises a new computing environment to the workstations,wherein the new computing environment includes at least one of anoperating system, application program, or device drivers.
 39. A systemcomprising: a plurality of workstations each having a computingenvironment; and a server computer coupled to the plurality ofworkstations over a network, wherein the server computer is configuredto perform operations comprising: receive from the workstations datarelated to the respective computing environments of the workstations;organize the workstations into groups based on at least one selectablecommon attribute among the received data; produce a deployment schedulecomprising at least one of the groups, the deployment schedule defininga time frame during which the workstations organized into the at leastone of the groups are to receive a new computing environment; andprovide a new computing environment to at least one of the workstations.40. The system of claim 39, wherein the data includes at least one of anorganizational entity associated with the workstations, a geographiclocation of the workstations, or the hardware or software residing onthe workstations.
 41. The system of claim 39, wherein the commonattribute among the received data includes at least one of anorganizational entity associated with the workstations, a geographiclocation of the workstations, or the hardware or software residing onthe workstations.
 42. The system of claim 39, further comprising adatabase to maintain the deployment schedule.
 43. The system of claim39, wherein the deployment schedule includes an entry indicatingavailability of a program to be used in producing the deploymentschedule.
 44. The system of claim 39, wherein the deployment scheduleincludes an entry indicating a time period during the time frame inwhich each of the workstations is to receive a program.
 45. The systemof claim 39, the server computer further comprising a graphical userinterface for displaying or updating the deployment schedule.
 46. Thesystem of claim 39, wherein the new computing environment includes atleast one of an operating system, application program, or devicedrivers.